In SAS Data Integration Studio 4.6 (SAS 9.3M2), the .sas file that is associated with the Deployed Job object can be written to the wrong SAS Workspace server. As a result, .sas files for the environment could be replaced with the code that was generated from another SAS^® Metadata server environment. This problem can occur when the directory path is the same for each environment.

You can see this problem by following these steps:

1. Launch SAS Data Integration Studio and connect to a server.
2. Import a package that contains a Deployed Job object. The .sas file is written to the correct location on that server.
3. Connect to a different SAS Metadata Server without closing SAS Data Integration Studio by selecting File ► Connection Profile.
4. Import a package that contains Deployed Job objects from another SAS Metadata server.
5. The .sas files that are associated with these Deployed Job objects are written to the server in which you connected to in Step 1.

As a result, the import is retaining connection information from the earlier SAS Metadata server connection instead of information from the current SAS Metadata Server connection.

As a workaround, close the SAS Data Integration Studio session and reopen the correct SAS Metadata server connection before you create the Deployed Job object.

SAS^® Clinical Data Integration 2.3 with SAS Data Integration 4.6 can also have this problem if the Deploy Job object has .sas code that is promoted from Test to QA or QA to Prod in the SAS Metadata server.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Data Integration Studio 4.6 is available at:

A fix for this issue for SAS Management Console 9.3_M2 is available at: